Automatic document classification via content analysis at storage time

ABSTRACT

Techniques are disclosed for efficiently and automatically classifying textual documents or files. In some embodiments, the classification process is integrated into or otherwise made part of the storage function, such that when the user initiates a save process for a given file, the file is processed through a classifier prior to (or contemporaneously with) completing the save function. In some such embodiments, textual content of the file is analyzed using natural language processing to identify a main or substantial concept discussed in the file, and one or more corresponding tags are then assigned to that file. Subsequently, the user can access that file based on the one or more tags, for instance, through a user interface that allows the user to select one or more content categories associated with the assigned tags. The files can be text-based, but may include other content as well, such as images, video, and audio.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/692,699 (filed 3 Dec. 2012), issued as U.S. Pat. No. 9,239,876, the entire disclosure of which is hereby incorporated by reference herein.

FIELD OF THE DISCLOSURE

This disclosure relates to document classification, and more particularly, to automatic classification of textual documents via content analysis that is carried out as part of storage function.

BACKGROUND

Online cloud-based document repositories are becoming popular places for users to store their content. There are a number of non-trivial issues that arise in the context of such operations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a document classification system configured in accordance with an embodiment of the present invention.

FIG. 2 illustrates a document classification system configured in accordance with another embodiment of the present invention.

FIG. 3 illustrates a document classification methodology configured in accordance with an embodiment of the present invention.

FIG. 4 illustrates a user interface methodology that can be employed by a document classification system, in accordance with an embodiment of the present invention.

FIGS. 5a-5d each illustrates an example screen shot of a graphical user interface that can be employed by a document classification system, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

Techniques are disclosed for efficiently and automatically classifying textual documents or files. In some embodiments, the classification process is integrated into or otherwise made part of the storage function, such that when the user initiates the save process for a given file, the file is processed through a classifier prior to (or contemporaneously with) completing the save function. In some such embodiments, textual content of the file is analyzed using natural language processing to identify the main concept or an otherwise substantial concept discussed in the document, and one or more corresponding tags are then assigned to that document. Subsequently, the user can access that document based on the one or more tags, for instance, through a user interface that allows the user to select one or more content categories associated with the assigned tags. The files can be text-based, but may include other content as well, such as images, video, and audio. The text to be analyzed may be provided as discrete text within the document. In addition, or alternatively, the targeted text can be extracted from images, audio, and/or video content. Numerous configurations and variations will be apparent in light of this disclosure.

General Overview

As previously explained, there are a number of non-trivial issues that arise in the context of storing content in cloud-based document repositories. For instance, the more files a given user decides to store in the cloud using an Internet-based service, the harder it becomes to locate a desired file (or files) later on. Sufficiently diligent users may invest the time to manually create an appropriate folder structure and assign each file accordingly. Other users may choose to take advantage of more flexible manual tagging facilities typically available. Such typical repository facilities generally necessitate a field-based metadata structure and/or keyword-based search with which the user must comply, and require discipline and up-front effort by the user, and further assume that the structure envisioned at the time of filing is still relevant at the time of retrieval. In addition, repository facilities that provide full-text content searching typically employ keyword-based search which may include synonyms, but generally lack the ability to identify concepts. For instance, a keyword-based full-text search using the term ‘transportation’ will not identify a document about aviation or airports if that document does not use the term ‘transportation’. Given such constraints and limitations, users of cloud-based diverse content repositories often resort to laborious scrolling through file listings, hoping the name of relevant files for which they are looking pop out.

Thus, and in accordance with an embodiment of the present invention, techniques are provided herein that utilize natural language processing (NLP) techniques to assist in automatically classifying textual content of files uploaded or otherwise provided to a content repository by a user. The repository may be, for example, an Internet-based storage or so-called cloud repository, or a local storage associated with the user's computing system/device or local area network (LAN). In some embodiments, as a file is uploaded or otherwise stored to the repository, it is passed through a semantic classification engine. The classification engine is configured to extract textual content of the file and to analyze that content and to produce a list of one or more suggested categories to which the file may be relevant. In some such embodiments, appropriate tags for each relevant category can then be assigned to that document. Tag assignment can be carried out, for example, by the cloud service and/or a tagging module in communication with (or integrated into) the classification engine. Numerous system configurations and varying degrees of integration or distributedness will be appreciated in light of this disclosure.

The analysis carried out by the classification engine may include, for instance, the review of the natural language in the file, so as to allow for not only word identification but also concept identification. Identifying a concept reflected in the content of a given document can be used to facilitate more accurate classification, and overcomes the previously noted limitation of keyword searching. Specifically, concept identification transcends mere association of meaning to single words, and instead looks at the collection of words analyzed to extract a more inclusive meaning of the overall content. This is why the category ultimately assigned to a given document may not be a word or phrase (or synonym thereof) that is actually used in the document.

The document to be classified and subsequently stored may be any file type and may have any format. The document may include, for instance, text only, but may also be a mixed media document that includes any combination of text, images, embedded video, embedded audio, and/or any other content. In some example cases, the text to be analyzed may be provided as discrete text comprising the file. In addition, or alternatively, the targeted text can be extracted from images comprising the document (for example, using image analysis and optical character recognition, OCR, to extract imaged text), audio comprising the document (for example, using an audio converter to extract aurally presented text), and/or video content comprising the document (for example, using OCR-based image analysis and/or audio-to-text conversion to extract imaged and/or aurally presented text).

Example document formats include portable document format (PDF), rich text format (RTF), American Standard Code for Information Interchange (ASCII), hypertext mark-up language (HTML or HTM or MHTML or MHT) format, spreadsheet format (for example, Adobe PageMaker, Microsoft Excel, etc), image format (for example, JPEG, BMP, etc), presentation format (for example, Adobe Presenter, Microsoft PowerPoint, etc), and word processing formats (for example, Microsoft Word, Corel WordPerfect, etc). In a more general sense, the document may include any type of file that has content that can be extracted into text form and then analyzed to identify one or more concept categories. As will be appreciated in light of this disclosure, the techniques provided herein can be used with any number of file types regardless of the media therein (for example, text, imagery, video, audio, etc), and the claimed invention is not intended to be limited to any particular file type.

There are numerous ways in which a user can take advantage of a repository populated in accordance with an embodiment of the present invention. For instance, a user may query a repository of files having assigned category tags as described herein so as to see a view of all files with a given tag (a sort of pseudo-folder or culled-down view that effectively lists only document files that satisfy the user query). For example, a search using the category tag of ‘transportation’ would list documents that discuss the concept of transportation, including a document about aviation or airports that does not actually use the term transportation. Likewise, the user may also retrieve all the documents with a given tag and collect them into a master document or portfolio or folder. A user could also specify multiple tags in a targeted search operation, such as a search where the categories of travel and accommodations/hotels are selected by the user.

In some embodiments, the user may also correct the automatically assigned categorization by manually adding, modifying, and/or removing tags. In some such example embodiments, the user-provided corrections provide valuable feedback that can be processed through a learning module, which can be used to tune or otherwise train the classification engine based on perceived user preferences. The user may also expressly provide preferences, if so desired. Numerous auto-refining schemes to train or otherwise customize the classification process per user feedback and preferences can be used, as will be appreciated in light of this disclosure.

System Architecture

FIG. 1 illustrates a document classification system configured in accordance with an embodiment of the present invention. As can be seen, the system of this example embodiment is integrated into a user's computing system, which may be, for example, a desktop or laptop computer, a workstation, a tablet, a smartphone, a game console, a set-top box, or other such computing devices. The system generally includes an application, a touch screen display, a content analysis section configured with a classification module and a user interface module, and a storage. Other componentry and modules typical of a computing system, such as processors (for example central processing unit and co-processor, graphics processor, etc), input devices (for example, keyboard, mouse, touch pad, etc), and operating system, are not shown but will be readily apparent in light of this disclosure.

In operation, the user can interact with the application to generate both storage requests and access requests. A storage request from the application can be provided to the classification module which classifies textual content of the file associated with a given request, and then stores that file along with its classification information. Note the application may be used to access external content, such as content found elsewhere on a network with which the system is communicatively coupled (for example, LAN and/or wide area network such as Internet). The user can also access any classified files as well as any unclassified files, and can also provide feedback to the classification module, via the user interface module. The touch screen allows interaction with the application and user interface module, although any number of other suitable interaction mechanisms can be used.

The application may be any application that allows a user to create, store, or otherwise access content having a textual content, whether in the form of discrete text or in another form that can be effectively extracted into text as previously explained. For instance, the textual content may be image-based text that is extracted via an image analysis and OCR process. Alternatively, or in addition to, the textual content may be audio-based text that is extracted using an audio-to-text conversion process. Alternatively, or in addition to, the textual content may be video-based text (which effectively may include image-based text and/or audio-based text) that is extracted using an OCR-based image analysis process and/or an audio-to-text conversion process. The application may be, for instance, a word processing application, a spreadsheet application, a presentation application, a browser application, an image processing application (for example, Adobe Photoshop), a multimedia application (for example, Adobe Director), an email application, a texting or messaging application, a desktop publishing application, or any other application that can effectively create and/or access, or otherwise operate with and store arbitrary and diverse textual content files. Note that the application may be used to create the content in some cases, but in other cases the application may be used to store content that has been created elsewhere.

The touch screen can be implemented with any suitable touchscreen technology. Other embodiments may not include a touch screen, but may instead include a regular display (for example, LCD, CRT, etc) along with input devices such as a keyboard and mouse. Other embodiments may include both touch screen capability and other input devices such as keyboards, mouse, touch pads, etc. The claimed invention is not intended to be limited to any particular type of input devices.

The classification module is programmed or otherwise configured to intercept or otherwise receive storage requests so that storage bound content can be classified as part of the storage function, in accordance with an embodiment. In some example embodiments, the storage request includes a file to be stored. In other embodiments, the storage request may include an address or pointer that indicates where the file to be stored is currently located. In any case, access to the file to be stored is provided to the classification module which is further configured to extract textual content from that file and to analyze that content to identify one or more categories to which that file can be assigned. The classification process itself can be carried out by a classification engine (within the module) that is implemented using any number of commercially available or proprietary classification engines capable of automatically concept tagging or otherwise classifying files into concept bins/categories, in accordance with some embodiments. Example text extraction and classification engines include Salience by Lexalytics, Lingo3D by Carrot Search, IDOL by Autonomy, and AlchemyAPI by AlchemyAPI. There are also a number of open source tools available, such as the Natural Language Toolkit by NLTK.org and the DragonTookKit from Drexel University. Other concept classification engines can be used as well, and the claimed invention is not intended to be limited to any particular classification engine.

As previously explained, the classification module may be further configured to extract text from media types other than straight text, in accordance with some embodiments. Thus, the classification engine within the classification module may be supplemented by, for example, an image processing engine that is configured to carry out OCR on images so as to extract text from those images. Once the text is liberated from the image by the OCR process, it can then be provided to the classification engine of the classification module. Similarly, once text is extracted from an audio file or a video file, it can then be provided to the classification engine. There are numerous commercially available online or desktop tools capable of carrying out image-based text extraction and audio-based text extraction (for example, SimpleOCR by SimpleSoftware, OpenOCR by Cognitive Technologies, and Dragon Speech Recognition by Nuance). Any such techniques can be implemented, for example, in a module operatively coupled to the input of classification module.

In general, one way to think about classification is to imagine some multi-dimensional space in which the content of each document or file is represented by a point in that space. Files have content that is similar are located close to each other, and documents of dissimilar content are farther away. In accordance with an embodiment of the present invention, imagine that a set of fixed points is located in that space, and those points represent various categories into which files to be saved can be filed. For a given file, the so-called ‘distance’ from that file to each of the category locations can be measured by the classification process. As will be appreciated, distance in this example context refers to how well, or the degree to which, a given file to be saved fits within a given category. A document/file can be classified in the category, for example, which has the shortest distance or in multiple categories that have a distance within a given threshold.

Thus, once the textual content of the file being saved is extracted and classified, the classification module may be further configured to assign that file to one or more categories based on its classification, in accordance with an embodiment of the present invention. The categories can vary from one embodiment to the next and may include, for example, any number of diverse categories that cover a broad range of distinct topics and fields, or any number of diverse categories that cover a broad range of distinct topics with a given field, or some combination thereof. In some embodiments, a pre-defined set of categories that will be of general use can be provided. The number of categories can vary greatly, but in some embodiments is in the range of 50 to 100 categories. One identified, these categories can then be used to configure and train an appropriate classification engine. As will be appreciated in light of this disclosure, the categories provided can be set as desired and may depend on factors such as the classification engine employed and the type of content preferred or otherwise stored by the user. Table 1 shows an example set of categories, in accordance with an embodiment. Numerous other category concept schemes can be used (for example, numerous diverse subject matter across numerous fields and/or numerous diverse topics within a single given field, depending on the application), and the claimed invention is not intended to be limited to any particular set of category concepts.

TABLE 1 Example Concept Categories Advertising Computer Health Politics Social Media Hardware Agriculture Contracts Home Presentations Sociology Art Crime Hotels Real Estate Software and Internet Auto Disasters Intellectual Receipts Space Property Aviation Economics Investing Recipes Sports Banking Education Labor Religion Technology Beverages Elections Law Renewable Traditional Energy Energy Biotechnology Fashion Marriage Resumes Travel Books Finance Mobile Devices Robotics Video Games Business Food Philosophy Science War Weather

The storage can be implemented, for example, with any suitable type of memory, such as a disk drive included in, or otherwise in communication with, the user's computing system. Other suitable memories include flash memory, random access memory (RAM), a memory stick or thumb drive, USB drive, etc. The storage is shown as local to the user, but as will be appreciated in light of this disclosure, the memory may also be remote to the user, such as a server-based memory associated with a given cloud storage service. In a more general sense, any memory facility can be used to implement the storage. Once a save function for a given file is initiated and the file is classified, the now classified file is stored in the storage to complete the save function initiated by the user.

The category tag(s) assigned to the file by the classification module can be stored with the file, for example, as content metadata or hidden data otherwise associated with the file. In some embodiments, the storage includes a lookup table (LUT) structure, where the table is indexed by the tags, such as shown in the example of Table 2. In such cases, a retrieval request

TABLE 2 Tag-based Lookup Table Category Tags Files Agriculture Farming.pdf Hiring a Veteran.pdf Art Guide to Impressionism Auto Top 10 Drivable Roads.pdf Aviation <none> . . . . . . Video Games <none> War Local Veteran Support.pdf Hiring a Veteran.pdf Weather East Coast Fault Line.pdf to the storage will return all files associated with the tag(s) included in the request. Note that not all tags need to be associated with files, and that some tags may be associated with multiple files. Further note that a given file may be associated with multiple tags. In other embodiments, the title of the file can be modified to include the tag(s) or a suitable abbreviation thereof as a suffix or prefix to the existing title as shown in the example of Table 3, so a retrieval request indicating

TABLE 3 Example Tagged Files Tagged Files Agr_Farming.pdf Agr_Hiring a Veteran.pdf Art_Guide to Impressionism Aut_Top 10 Drivable Roads.pdf <none> <none> War_Local Veteran Support.pdf War_Hiring a Veteran.pdf Wea_East Coast Fault Line.pdf one or more tags will similarly return the files of interest. Thus, the user can access and view external content using the computing system and, if so desired, save that content to the computing system by way of the classification module. As further shown, the storage may further include unclassified files if so desired, which may be saved to the memory directly by a given application rather than through the classification module. In some embodiments, such unclassified files can be accessed by the classification module during a re-save request initiated by the user and re-saved into the classified part of the storage.

The user interface module is programmed or otherwise configured to intercept or otherwise receive file access requests so that stored content can be accessed as part of the retrieve or search function, in accordance with an embodiment. In some example embodiments, the access request may specify a file to be retrieved, such as specific files stored in the classified files w/textual content portion and/or the unclassified file portion of the storage. Alternatively, in some embodiments, the access request may specify one or more categories associated with files to be retrieved. In the example embodiment shown, the user interface module is configured to receive a file access request from the application, and to present the user with a graphical user interface (via the touch screen display) that allows the user to select or otherwise specify the particular files of interest, by either selecting file names and/or content categories. FIGS. 5a-d illustrate example graphical user interfaces configured in accordance with some such embodiments, and will be discussed in turn.

The user interface module of this example embodiment is further configured to allow the user to provide feedback to the classification module. For instance, the user may view the various available content categories, add additional content categories, modify or delete existing content categories, and/or change the category (or categories) to which a given file is assigned. In some embodiments, the classification engine in the classification module is effectively capable of learning based on such user input and can recalibrate or otherwise change its classification process so that future classifications reflect the user feedback. In some such cases, the classification module may be further configured to re-classify the previously classified files stored in the classified files w/textual content portion of the storage. Any number of classification engine training techniques can be employed to provide customized classification based on specific user feedback.

The classification module will be discussed in further detail with respect to FIG. 3. Likewise, the user interface module will be discussed in further detail with respect to FIGS. 4 and 5 a-d. In the meantime, FIG. 2 illustrates a document classification system configured in accordance with another embodiment of the present invention. This system is similar to the system shown in FIG. 1, except that the user interface module is executing or otherwise implemented on a client that is remote to an application server upon which the classification module is executing. Such a client-server embodiment may be suitable, for example, for use in the context of an online repository service that allows a user/client to upload files via the server for storage. Note that the user interface module may be installed local to the client, or an applet or other downloadable module that can be provisioned in real-time to a client requesting access to the cloud service (for example, any Internet-based storage service). In one such embodiment, the user interface module is provisioned in real-time to the client as a JavaScript applet in response to a user request for access to the cloud service, but any other suitable code and provisioning schemes can be used, as will be appreciated.

In operation, a user can access files stored locally to the user in the file system, and may also access files stored remotely to the user such as files downloaded or otherwise accessed via the Internet or other communication network (for example, local and/or wide area network of a company, etc). The file system of the user computing system can be implemented with any number of suitable file storage schemes. Likewise, the user's client can be implemented with any suitable computing device (for example, laptop, desktop, tablet, smartphone, etc). The user interface module (UI) executing on the client may be configured to allow for file access as typically done, and may be further configured with user interface capability to allow for the issuance of user storage and access requests as described herein. The requests can be communicated to the application server via the network (for example, which may include, for instance, a LAN operatively coupled to the Internet).

Storage requests can be carried out in a similar fashion as previously described with reference to FIG. 1, wherein the classification module executing on the server receives the storage request and textual content is then extracted from the file to be stored via the content extraction module. The extracted textual content is then classified via the classification engine using any number of known concept classification techniques, such as those previously described. The classified file(s) can then be stored in the cloud storage. Likewise, access requests can be carried out in a similar fashion as previously described with reference to FIG. 1, wherein the application server receives the access request via the UI executing on the client provides access to the appropriate file(s) that satisfy that request. The classified file(s) stored in the cloud storage can be returned to the client via the network and displayed to the user via the UI executing on the client.

The UI executing on the client may be further programmed or otherwise configured to allow the user to provide feedback to the classification module as previously explained. In the example embodiment of FIG. 2, the feedback data provided by the user can be stored in the analytics storage. Thus, files may flow through the system in a number of ways. In one example case, the user may choose a file from the local file system, and then upload that file to the cloud service application server. The application server may then store the content of the file in the cloud storage system, extract textual content from the file, and send textual content to the classification engine for analysis. Note that order of these storage-based functions may vary (for example, store-extract-send-analyze, or extract-send-analyze-store, or extract-store-send-analyze, or extract-send-analyze/store where analysis and storing occur at least partially at the same time, etc), but when considered in the aggregate, form a complete storage function that is responsive to a user-initiated storage request, in accordance with an embodiment of the present invention. In any such cases, the classification engine may then return suggested categories, and the application server may assign corresponding tags to the file and stores this information in the cloud storage. The user can subsequently view all files assigned to a given category, and can also see the categories assigned to a given file. In addition, the user can adjust the assigned categories, which in turn updates the tag information associated with the stored file. User-initiated updates can be collected and analyzed to improve the algorithms in the classification engine.

As will be appreciated in light of this disclosure, the various modules and components of the system, such as the classification and user interface modules, can be implemented in software, such as a set of instructions (for example C, C++, object-oriented C, JavaScript, BASIC, etc) encoded on any computer readable medium (for example, hard drive, server, or other suitable memory), that when executed by one or more processors, cause the various methodologies provided herein to be carried out. In other embodiments, the components/modules may be implemented with hardware, such as gate level logic (for example, FPGA) or a purpose-built semiconductor (for example, ASIC). Still other embodiments may be implemented with a microcontroller having a number of input/output ports for receiving and outputting data, and a number embedded routines for carrying out the functionality described herein. Any suitable combination of hardware, software, and firmware can be used.

Storage-Based Classification Methodology

FIG. 3 illustrates a document classification methodology configured in accordance with an embodiment of the present invention. As can be seen, the methodology of this example embodiment includes a number of phases or sub-processes including a user-initiated storage/upload sub-process, a classification sub-process, and complete storage/upload sub-process. This method may be implemented, for example, by either of the classification modules shown in FIGS. 1 and 2, respectively. As previously explained, the order of these sub-processes may vary from one embodiment to the next, but when considered in the aggregate, from a complete storage function that is responsive to a user-initiated storage request, in accordance with an embodiment of the present invention.

The method commences with receiving 301 a user request to store a file. The request may be provided locally as shown in FIG. 1 or remotely as shown in FIG. 2. In any case, this request triggers the classification sub-process, which may also be carried out locally as shown in FIG. 1 or remotely as shown in FIG. 2. The classification sub-process of this example embodiment includes determining 303 whether the file is already classified. If not, then the method continues with extracting 305 textual content from the file and analyzing 307 the extracted textual content to identify one or more conceptual categories to which it applies. This analysis may include, for example, typical analysis performed by any of the concept classification tools previously discussed (for example, Salience by Lexalytics, Lingo3D by Carrot Search, IDOL by Autonomy, and AlchemyAPI by AlchemyAPI), and/or any other suitable classification schemes/tools.

The classification sub-process continues with optionally providing 309 the user with one or more identified categories. In this example embodiment, the user is then given an opportunity to review the provided categories pre-storage. In particular, the classification sub-process of this example case further includes determining 311 if the user likes the provided categories. If so, the classification sub-process continues with assigning 317 the corresponding tag(s) to the file. Further note that, in cases where the determination at 303 indicates that the file is already classified, then the classification sub-process jumps to the determination at 311. In this case, if the user likes the provided categories, then no new tags need to be assigned and the classification sub-process continues with keeping 317 the existing tags associated with file. Once the tags are assigned or otherwise established as acceptable, the methodology continues with storing 319 the file along with tag information. Again, this storage may be provided locally as shown in FIG. 1 or remotely as shown in FIG. 2.

If the determination at 311 indicates that the user does not like the provided categories, the classification sub-process may optionally include adjusting 313 the tags per user feedback. In some such cases, the classification sub-process may optionally further include analyzing 315 the changes and refining or otherwise training the classification engine accordingly, so that future file classifications will reflect that user feedback, as indicated by the dashed line from 315 to 307.

Note in this example embodiment that the user has the optional opportunity to verify the desirability of the tagging in real-time before the document is stored or as a part of the document storage process. In another example embodiment, and as further indicated in FIG. 3, the process flow may proceed from 307 directly to 317, wherein the tags are assigned at storage time with no real-time user review or classifier optimization. However, in some such cases, the user may examine the tags and revise as desired, as a post-storage activity. For instance, in one such case, the functions at 309, 311, 313, and 315 can be carried out sometime after 319. Numerous variations on the overall storage-based classification methodology will be apparent in light of this disclosure.

User Interface Methodology

FIG. 4 illustrates a user interface methodology that can be employed by a document classification system, in accordance with an embodiment of the present invention. This method may be implemented, for example, by either of the user interface modules shown in FIGS. 1 and 2, respectively.

The methodology commences with receiving 401 a user access request to retrieve one or more files, and determining 403 if that request specifies a category. As will be appreciated, classified files as described herein can be associated with one or more concept categories and corresponding tags that assist with efficiently providing a user access to those files. If the request does not specify a category, the methodology continues with presenting 405 the user with a graphical user interface (GUI) identifying available categories of text files, and subsequently receiving 407 one or more selected categories from the user. FIG. 5a illustrates an example screen shot of a graphical user interface that can be presented to the user at 405, in accordance with an embodiment of the present invention. As can be seen, the GUI includes a number of user selectable file categories, which in this example case cover a broad range of diverse content and subject matter. Below the user selectable file categories is a listing of all the available files, along with a scroll bar user interface. Note that all the available files are shown, because no user selection in the user selectable file categories has been provided yet. FIG. 5b shows an example case where the user has made a selection in the user selectable file categories, by checking the Auto radio button (or any other suitable user selection mechanism). This selection of the Auto category can be the selected category received at 407, in accordance with some embodiments.

If, on the other hand, the access request from the user does specify a category, the methodology continues with retrieving 409 any files tagged with the specified category or categories, and then determining 411 if the retrieved file(s) should be displayed or foldered. If displayed, then the methodology continues with displaying 413 the files tagged with the specified category (or categories). For instance, FIG. 5b shows an example GUI display of files, which is effectively a culled down version of the total files shown in FIG. 5a , in response to the user selection of the Auto category. As previously explained, note that some of the files retrieved may not even use the term ‘auto’, but rather discuss concepts that can be generally classified as having to do with the concept category of Auto. FIG. 5c shows an example GUI display of files in accordance with another embodiment, wherein the total files shown in FIG. 5a are still shown but files associated with unselected categories are greyed out (or otherwise minimized), in response to the user selection of the Intellectual Property category. Numerous display schemes can be used, and the claimed invention is not intended to be limited to any particular such scheme.

If, on the other hand, the determination at 411 indicates a preference of foldering, then the methodology of this example embodiment continues with receiving 415 a folder designation from the user, and outputting 417 the retrieved files to designated folder. FIG. 5d shows an example GUI display of files in accordance with one such embodiment, wherein the total files shown in FIG. 5a are still shown but files associated with unselected categories are greyed out (or otherwise minimized), in response to the user selection of the Investing, Renewable Energy, and Traditional Energy categories. In addition, the user is being given an opportunity to save the retrieved (darkly displayed) files to a folder or portfolio, by virtue of a pop-up window (or any other suitable such user interface mechanism). The user can also select Cancel in the pop-up window to only display the files.

Numerous embodiments will be apparent, and features described herein can be combined in any number of configurations. One example embodiment of the present invention provides a file classification system. The system includes a content extraction module configured to, in response to a storage request for a file, extract textual content of the file. The system further includes a classification engine configured to analyze the extracted textual content to determine a concept category to which the file can be assigned, and to assign corresponding tag information to the file. In some cases, the system further includes a storage for storing the file and its tag information. In some such cases, the storage is Internet-based storage that is remote to system user. In other such cases, the storage is local to system user. In some cases, the system includes a user interface module configured to receive user access requests to retrieve stored files that have been classified by the classification engine. In some cases, the system includes a user interface module configured to receive access requests that specify tag information, and to retrieve stored files that have been assigned that tag information by the classification engine. In some cases, the system includes a user interface module configured to provide a full listing of stored files classified by the classification engine, and to provide a culled listing of those files in response to a file access request that specifies tag information, wherein the culled listing highlights or otherwise indicates files that have been assigned that tag information by the classification engine. In some cases, the system includes a user interface module configured to allow a user to review at least one of the concept category and/or tag information assigned to the file, and to receive user updates with respect to same. In one such case, the classification engine is further configured to refine classification it carries out based on the user updates. In some cases, the system is further configured to store the file and its tag information.

Another embodiment of the present invention provides a file classification system. In this example case, the system includes a storage. The system further includes a classification module configured to, in response to a storage request for a file, extract textual content of the file, analyze the extracted textual content to determine a concept category to which the file can be assigned, assign corresponding tag information to the file, and save the file and tag information in the storage. The system further includes a user interface module configured to receive access requests that specify tag information, and to retrieve stored files from the storage that have been assigned that tag information by the classification module. In some cases, the storage is Internet-based storage that is remote to system user. In other cases, the storage is local to system user. In some cases, the storage and content analysis module are part of an Internet-based storage service. In one such case, the user interface module is provisioned in real-time to a remote client that has access to the Internet-based storage service. In some cases, the user interface module is further configured to provide a full listing of stored files classified by the classification module, and to provide a culled listing of those files in response to a file access request that specifies tag information, wherein the culled listing highlights or otherwise indicates files that have been assigned that tag information by the classification module. In some cases, the user interface module is further configured to allow a user to review at least one of the concept category and/or tag information assigned to the file, and to receive user updates with respect to same. In some cases, the classification module is further configured to refine classification it carries out based on the user updates.

Another embodiment of the present invention provides a file classification methodology. The method includes, in response to a storage request for a file, extracting textual content of the file. The method further includes analyzing the extracted textual content to determine a concept category to which the file can be assigned, assigning corresponding tag information to the file, and storing the file and its tag information. In some cases, storing the file and its tag information is carried out using Internet-based storage that is remote to system user. In some cases, storing the file and its tag information is carried out using a storage local to system user. In some cases, the method includes receiving user access requests that specify tag information, and retrieving stored files that have been assigned that tag information. In some cases, the method includes providing a full listing of stored files, and providing a culled listing of those files in response to a file access request that specifies tag information, wherein the culled listing highlights or otherwise indicates files that have been assigned that tag information. In some cases, the method includes allowing a user to review at least one of the concept category and/or tag information assigned to the file, and receiving user updates with respect to same. In some such example cases, the method further includes refining file analysis based on the user updates. Numerous variations will be apparent in light of this disclosure. For example, another embodiment of the present invention provides a computer readable medium having instructions encoded thereon that when executed by one or more processors cause a file classification process to be carried out, wherein the process includes functionality as variously defined in this paragraph.

The foregoing description of example embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. 

What is claimed is:
 1. A computer readable medium having instructions encoded thereon that, when executed by one or more processors, cause a file classification process to be carried out, the process comprising: extracting textual content from a first file; analyzing the extracted textual content to determine one or more tags that correspond to the textual content; assigning an initial categorization to the first file, wherein the initial categorization is associated with the one or more tags that correspond to the textual content; displaying, to a first user, the initial categorization that was assigned to the first file; receiving a modified categorization from the first user; and associating the one or more tags with the modified categorization.
 2. The computer readable medium of claim 1, wherein the textual content is extracted from the first file in response to a storage request for the first file.
 3. The computer readable medium of claim 1, wherein: the initial categorization comprises a first set of one or more categories; the modified categorization comprises a second set of one or more categories; and the second set includes at least one of the categories in the first set.
 4. The computer readable medium of claim 1, wherein the file classification process further comprises assigning the modified categorization to the first file.
 5. The computer readable medium of claim 1, wherein the file classification process further comprises: identifying a second file containing textual content, wherein the one or more tags also correspond to the textual content contained in the second file; and assigning the modified categorization to the second file.
 6. The computer readable medium of claim 1, wherein: the initial categorization comprises a first set of one or more categories; the modified categorization comprises a second set of one or more categories; and the second set does not include at least one of the categories in the first set.
 7. The computer readable medium of claim 1, wherein: the initial categorization comprises a first set of one or more categories; the modified categorization comprises a second set of one or more categories; and the second set does not include any of the categories in the first set.
 8. The computer readable medium of claim 1, wherein the file classification process further comprises: assigning the modified categorization to the first file; generating an association between the modified categorization and a filename for the first file; and storing the association in a lookup table.
 9. The computer readable medium of claim 1, wherein: the file classification process further comprises receiving an access request to retrieve the first file; and the access request includes the modified categorization.
 10. The computer readable medium of claim 1, wherein: the first file is stored in a storage repository; and the file classification process further comprises searching the storage repository for a second file that contains textual content, wherein the one or more tags also correspond to the textual content contained in the second file.
 11. The computer readable medium of claim 1, wherein the textual content is extracted from the first file in response to a storage request for the first file, wherein the storage request is received form a second user.
 12. A file classification methodology, comprising: analyzing textual content contained within a file to determine an initial classification for the file, wherein the initial classification comprises one or more concept categories to which the file can be assigned; presenting the initial classification to a user; receiving, from the user, a modification to the initial classification, wherein the modification comprises user input selected from a group consisting of (a) a removal from the initial classification of a particular one of the one or more concept categories, and (b) an addition to the initial classification of a new concept category; and assigning, to the file, a modified classification based on the modification to the initial classification.
 13. The file classification methodology of claim 12, wherein the textual content is analyzed in response to receiving, from the user, a storage request for the file.
 14. The file classification methodology of claim 12, wherein: the textual content is analyzed in response to saving the file in a document repository; and the methodology further comprises retrieving the file from the document repository before analyzing the textual content contained within the file.
 15. The file classification methodology of claim 12, wherein receiving the modification to the initial classification comprises displaying a plurality of selectable checkboxes associated with a corresponding plurality of classifications.
 16. The file classification methodology of claim 12, wherein: analyzing the textual content further comprises determining one or more tags that correspond to the textual content; and the initial classification is a classification that is associated with at least one of the one or more tags.
 17. A file classification system, comprising a memory device and a processor that is operatively coupled to the memory device, wherein the processor is configured to execute instructions stored in the memory device that, when executed, cause the processor to carry out a file classification process that comprises: in response to receiving, from a first user, a storage request for a file, extracting textual content of the file, analyzing the extracted textual content to determine a concept category to which the file can be assigned, assigning corresponding tag information to the file, and storing the file in a file repository; receiving an access request from a second user that specifies query tag information; identifying files stored in the file repository that have been assigned tag information that corresponds to the query tag information; and displaying a listing of the identified stored files to the second user.
 18. The file classification system of claim 17, wherein identifying files stored in the file repository comprises looking up the query tag information in a lookup table that correlates tag information to a plurality of filenames.
 19. The file classification system of claim 17, wherein identifying files stored in the file repository is performed without accessing the file repository.
 20. The file classification system of claim 17, wherein the file classification process further comprises: displaying, to the first user, the tag information assigned to the file; receiving modified tag information from the first user; and modifying the tag information that is assigned to the file based on the modified tag information received from the first user. 